Method and apparatus for enhancing universal serial bus application

ABSTRACT

A system for enhancing universal serial bus (USB) applications comprises an upstream processor, a downstream processor and a main controller. The upstream processor accepts standard USB signals from a USB host and independently provides responses required by USB specification within the required time frame. The upstream processor also contains storage for descriptors for a device associated with this upstream processor. The main controller obtains the descriptors by commanding the downstream processor, and passes them to the upstream processor. The downstream processor connectable to USB-compliant devices accepts the USB signals from the USB-compliant devices and provides responses required by USB specification within the required time frame. The main controller interconnects the upstream and downstream processors, and provides timing independence between upstream and downstream timing. The main controller also commands the downstream processor to obtain device descriptors independent of the USB host.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation-in-part application ofapplication Ser. No. 12/847,194 filed Jul. 30, 2010, now U.S. Pat. No.7,949,816, which is a continuation application of application Ser. No.11/821,986 filed Jun. 26, 2007, now U.S. Pat. No. 7,797,474, which is acontinuation application of application Ser. No. 11/360,304 filed Feb.22, 2006, now U.S. Pat. No. 7,246,189, which claims benefit of U.S.Provisional Application No. 60/738,115 filed Nov. 18, 2005, each ofwhich is incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION

The Universal Serial Bus (USB) is a connection standard which allows avariety of peripheral devices to be easily attached to computerssupporting the standard. It has become widely adopted.

The USB standard was created by an alliance of some of the largestcompanies in the computer and communication industry. The latestspecification defining USB is Revision 3.0 of November 2008, and is herereferred to as the “USB Specification”, which term can include futuremodifications and revisions. The USB standard is non-proprietary and ismaintained by an open industry organization known as the USB Forum. TheUSB Specification establishes a number of criteria, which must be met inorder to be compliant to USB standards. The USB Specification andinformation about the standard are available at www.usb.org.

The USB standard has the great advantage from the user's point of viewin that it permits peripherals to be readily connected to computingdevices often with no manual configuration to be made by an end user.

The USB is a strict master-slave bus. There is one USB master, usuallycalled “host”. The host acts as master of the bus, controlling allcommunications. Typically, the USB host is a computing device, such as apersonal computer. Devices, or peripherals, communicate with the hostonly if so commanded by the host. USB peripherals are defined by the USBspecification as being of two types: “hubs” and “functions”. “Functions”are referred to here as “USB-compliant devices” or “devices”. The USB isbased on a tiered star topology with one hub at the center of each star.Each “ray” from each “star” terminates in exactly one hub or device.Hubs convert a single upstream attachment point into multiple downstreamattachment ports. Either a device or another hub can be attached to sucha downstream port. In this manner, the USB specification limit of 127unique USB-compliant devices attached at any given time can be attained.Devices include computer peripherals such as keyboards, mice, joysticks, cameras, printers, external storage devices, multi-media devicesand the like. Since all device communications eventually converge at thehost, and there can be up to 127 devices on the same bus, timeallocation on the bus is extremely critical. The USB specificationaddresses this issue, and other issues, with a detailed definition ofelectrical signaling, data format and communication protocol. Briefly,the protocol divides time on the bus into one millisecond frames, whichmay be further subdivided into eight 125 microsecond microframes for thehigh speed version of the bus, defines a number of transfer types, andtightly controls timing, including the time of response from hubs orUSB-compliant devices to host commands. The tight timing control isnecessary to provide for maximum bus bandwidth while maintainingcommunication integrity and error checking.

The USB specification has made great advances in facilitating theconnection of up to 127 of a wide variety of devices to any USB-enabledcomputer, using only one connector type. In providing this capabilityand convenience, a number of tradeoffs had to be made, which result inlimiting the application of the USB in many situations. The followingthree USB specification requirements limit its application in manysituations. First, the tight timing specification has the consequencethat in practice devices have to be no further away from the host than30 meters. Even this can only be achieved by connecting five hubs inseries, since the cabling limit is 5 meters between a device and a hub.Both the relatively short absolute length of 30 meters and theinconvenience and cost of having to use five extra hubs are a limitationin many computer applications. Second, the USB specification allows anynumber of devices of the same type, such as several keyboards or severalmice, to be connected simultaneously. This is a desirable feature initself, since there are many applications where access to one computeris needed from several workstations. The disadvantage arises that allsuch devices have simultaneous access to the computer, allowing morethan one user to enter or alter data, for example, possibly resulting inerrors and undesirable results. Third, the tight timing specificationand protocol definition limit the ability to switch one device from onehost, or computer, to another. If the communications protocol is notadhered to or the timing specification violated during switching, thehost will detect an error, and after several recovery attempts, willdeclare the device “inoperable” and refuse to communicate with it. Inaddition, practical implementations of the USB specificationrequirements in commercially available computer operating systems thatsupport USB put a time limit on getting a response to requests to adevice. Even if no error is detected by the host, if a device continuesto NAK host requests, eventually the host will declare the device“inoperable”. This may happen if the device is not locally emulated, asis the practice in many existing products, but the device is accessed toobtain true responses from the device, and the device is at asignificant distance from the host. One way to switch one device fromone host to another is to either physically unplug it or to simulateunplug by appropriate signaling. Then to connect it to another host, orcomputer, by physically plugging it in or by simulating plug in byappropriate signaling. Both unplugging a device and plugging it in,result in a processing delay in the host. It takes the host time todetect device unplug, and additional time to detect and process deviceplug in. On plug in, the host goes through an extensive process, called“enumeration”, to determine the type and capabilities of a device and to“connect” it to the USB. These delays are undesirable in many computersystem applications.

Solutions that enhance USB in these areas would be very desirable inmany computer system applications. Especially desirable would be onesolution that overcomes all limitations indicated above. The presentinvention offers a solution to all the limitations identifiedhereinabove.

The prior art has addressed mainly the limitation in connection distancebetween a peripheral and the host. U.S. Pat. No. 6,363,085 to Samuelsdescribes the use of an active repeater. This system's ability toimprove the distance is limited, since it only decreases the propagationdelay in the cable, which does not result in a significant increase indistance. U.S. Pat. Nos. 6,571,305 and 6,922,748, both to Engler,describe a system consisting of two intelligent emulators. One, at thehost end, emulates a device, the second one, at the device end, emulatesa host. The device emulator satisfies all timing requirements to thehost, and the host emulator does the same at the device end. However,the information flow is limited to data from the peripheral device tothe host. There is no provision for the host to determine the nature anddetailed capabilities of the connected device, since the communicationschannel in the direction from the host to device carries only errorreports. That is, the host is not able to perform enumeration on thereal device, only on the device emulator. Many peripheral devices, whileconforming to USB definitions and specifications for a device type, alsohave unique features and capabilities. Such capabilities arecommunicated to the host in response to host requests duringenumeration, which will not be made known to the host in this system.The system is thereby limited to handle only devices that arespecifically emulated in the device emulator. The lack of acommunications channel from host to device also prevents the host fromcommanding the device, which is needed in many devices. For instance,conventional keyboards have indicators that light to indicate Caps Lock,Num Lock and Scroll Lock. Engler has no provisions for suchcapabilities. Engler also does not have capability to signal the hostwhen a device, as opposed to the device emulator, has been plugged in orunplugged. U.S. Pat. No. 6,381,666 to Kejser et al., describe an“extended range hub”, consisting of a Local Expander and a RemoteExpander. In similarity to Engler, two units are provided. One, theLocal Expander, is located at the host. The second, the Remote Expander,is located at the device. This system improves on Engler by providingfor host request pass-on to the real device. However, Kejser does notprovide for error handling, and does not provide for timing managementto prevent running into the babble condition at the Remote Expandereither on sending data to the remote device or requesting data from it.Kejser also does not treat the “high-speed” protocol features,introduced by revision 2.0, the current revision of the USBspecification, such as split transactions, the NYET handshake, nor“chirp” or “squelch” signaling. Similar to Kejser, U.S. Pat. No.6,954,808 to Russell describes an USB extension system consisting of twohubs, a transmitter hub and a receiver hub, interconnected by a non-USBcompliant link. Russell has no provisions to insure that the hub locatedat the host, the transmitter hub, is able to respond to hostcommunications within the time required by the USB specification,instead response timing is dependent on timing from the device and thespeed of the communications channel between the two hubs. U.S. Pat. No.6,708,247 to Barret et al. describes a system consisting of a hostcontroller and a remote hub, interconnected by a non-USB compliant bus.Barret requires that the host controller be modified in accordance withthe invention. U.S. Pat. No. 6,961,798 to Ferguson provides forextension of certain USB devices via non-USB communications media.However, the invention requires that the host be modified withtransmitter circuits of the invention. U.S. Pat. No. 6,934,793 to Yinget al. treats sharing one USB device among up to four PC hosts. However,there is no provision in Ying's multiplexer to assure that the timingrequirements of the USB specification are met or any provisions to avoidcollision of communications from the plurality of PC's. None of theabove prior art covers the situation where an USB-compliant device ormultiple devices connect selectively to a number of USB hosts whilemeeting the timing requirements of the USB specification, nor do theycover the situation where multiple USB-compliant devices connect to thesame host and are enabled selectively while meeting the timingrequirements of the USB specification, nor the use of standard,unmodified USB hosts, hubs, and USB-compliant devices, nor provide trueenumeration responses for a wide class of devices.

It would be advantageous to have a method and system that does not havesuch limitations and omissions, and that handles the additional protocolcases and conditions introduced by revision 3.0 of the USBspecification, including handling USB high-speed and super speedcommunications, and requires no modifications to USB hosts, hubs or toUSB-compliant devices.

The present invention overcomes these limitations and providesenhancements in connection separation length between USB-compliantdevice and USB host, in switching one or more devices among many hostsand in connecting many devices to the same host with control over theircommunications such that they do not interfere with one another, and inproviding to the host true enumeration responses from USB-compliantdevices, not just emulating them. The present invention requires nochanges or modifications to USB hosts, hubs or to USB-compliant devices;standard hosts, hubs and devices can be used with the current invention.

OBJECTS AND SUMMARY OF THE INVENTION

An object of the present invention is to provide a system and techniquefor switching one USB-compliant device among multiple USB hosts withoutdisconnecting the device from each host, and while meeting all USBspecification requirements, including timing, at the host and the deviceand providing capabilities for the hosts to determine the nature, typeand capabilities of the device.

An object of the present invention is to provide a system and techniquefor switching a group of USB-compliant devices as a unit among multipleUSB hosts without disconnecting the devices from each host, and whilemeeting all USB specification requirements, including timing, at thehosts and the devices and providing capabilities for the hosts todetermine the nature, type and capabilities of the devices.

An object of the present invention is to provide a system and techniquefor switching multiple USB-compliant devices among multiple USB hostswithout disconnecting the devices from each host, and allowingsimultaneous connection of several devices to several hosts, each deviceconnected to a different host, and while meeting all USB specificationrequirements, including timing, at the hosts and the devices andproviding capabilities for the hosts to determine the nature, type andcapabilities of the devices.

An object of the present invention is to provide a system and techniquefor switching multiple groups of USB-compliant devices as a unit amongmultiple USB hosts without disconnecting the devices from each host, andallowing simultaneous connection of several groups of devices as a unitto several USB hosts, each group connected to a different host, andwhile meeting all USB specification requirements, including timing, atthe hosts and the devices and providing capabilities for the hosts todetermine the nature, type and capabilities of the devices.

An object of the present invention is to provide a system and techniquefor several USB-compliant devices of the same type but not necessarilyidentical in model to be connected selectively to one USB host withoutinterfering with one another and while meeting all USB specificationrequirements, including timing, at the host and the devices andproviding capabilities for the host to determine the nature, type andcapabilities of the devices.

An object of the present invention is to provide a system and techniquefor groups of several USB-compliant devices of the same type but notnecessarily identical in model to be connected to one USB host as agroup without one group interfering with another and while meeting allUSB specification requirements, including timing, at the host and thedevices and providing capabilities for the host to determine the nature,type and capabilities of the devices.

An object of the present invention is to provide a system and techniquefor connecting USB-compliant devices to an USB host while positionedbeyond the distance limits resulting from the USB specificationrequirements, while complying with all USB specification requirementsincluding signal timing at the host and the device and providingcapabilities for the host to determine the nature, type and capabilitiesof the device, while achieving the previously stated objectives.

An object of the present invention is to provide a system and techniquefor connecting USB-compliant devices to an USB host while positionedbeyond the distance limits resulting from the USB specificationrequirements, while complying with all USB specification requirementsincluding signal timing at the host and the device and with time limitsto receive valid responses, such limits being part of USB host, andproviding capabilities for the host to determine the nature, type andcapabilities of the device, while achieving the previously statedobjectives.

An object of the present invention is to provide a system and techniquefor switching a group of USB-compliant devices as a unit among many USBhosts without disconnecting the devices from each host while positionedbeyond the distance limits resulting from USB specificationrequirements, and while meeting all USB specification requirements,including timing, at the hosts and the devices and providingcapabilities for the hosts to determine the nature, type andcapabilities of the devices.

An object of the present invention is to provide a system and techniquefor groups of several USB-compliant devices of the same type but notnecessarily identical in model to be connected selectively to one USBhost as a group without one group interfering with another whilepositioned beyond the distance limits resulting from USB specificationrequirements and while meeting all USB specification requirements,including timing, at the host and the devices and providing capabilitiesfor the host to determine the nature, type and capabilities of thedevices.

An object of the present invention is to provide a system and techniquefor switching multiple groups of USB-compliant devices as a unit amongmultiple USB hosts while positioned beyond the distance limits resultingfrom the USB specification requirements without disconnecting thedevices from each host, and allowing simultaneous connection of severalgroups of devices as a unit to several hosts, each group connected to adifferent host, and while meeting all USB specification requirements atthe hosts and the devices and providing capabilities for the hosts todetermine the nature, type and capabilities of the devices.

An object of the present invention that no modifications need to be madeto the USB host, the host USB controllers, root and other hubs or toUSB-compliant devices to provide such enhancements.

An object of the present invention to cover the full range of devicespeeds specified in the USB specification, low, full and high speed, andother speeds which may be specified in future revisions of the USBspecification, while achieving the previously stated objectives.

An object of the present invention to maintain data togglesynchronization among the USB-compliant device(s) and USB host(s), whileachieving the previously stated objectives.

An object of the present invention to provide for transmission of resumesignaling from USB-compliant device(s) to the host(s) for devices withthe remote wake-up feature, while achieving the previously statedobjectives.

An object of the present invention to provide for transmission of deviceattach (plug-in) or detach (plug-out) events signaling from device(s) tothe host(s), while achieving the previously stated objectives.

In accordance with an embodiment of the present invention, the systemcomprises one or more processing elements handling connections to one ormore USB hosts and one or more processing elements handling connectionsto one or more USB-compliant devices, hereinafter called “devices”, theprocessing elements connected by a main controller processing element,which includes routing and attachment topology management functions.Only the signals in the connections to the USB host(s) and to the USBdevice(s) conform to the USB specification standards. All other signalsare optimized to fit their particular role.

In accordance with an embodiment of the present invention, the apparatuscomprises one or more properly programmed microprocessors, or otherdigital processing engines, controlling one or more USB serial interfaceengines (SIE), connected to one or more USB hosts on the upstream sideand to one or more devices on the downstream side. An upstream (US) SIEconnects to a USB host and decodes messages and data on the USB, acceptsthose addressed to it, and sends messages and data in the appropriateUSB format. A downstream (DS) SIE connects to USB peripherals, which maybe devices or hubs, and decodes messages and data on the USB and sendsmessages and data in the appropriate USB format addressed to aparticular peripheral. The microprocessor is programmed to control oneor more US SIE's to accept commands and data, and to provide to the USUSB any data received from downstream that is destined to the particularupstream connection. It is further programmed to provide to the DS SIE'sdata received from upstream and destined to the particular downstreamconnection. The microprocessor further contains buffers to hold messagesfrom the USB for analysis to determine the required action, to serve aspart of the communications medium between upstream and downstream, andto format and hold outgoing upstream and DS USB messages. USB hubs areincorporated in one embodiment of the invention when more than onedevice is to be connected to a particular host computer. The hub isplaced between the US SIE and the upstream connection to an USB host andgroups several US SIE's into one physical connection to the host.

It would be appreciated by one of ordinary skill in the art that anyapparatus that can interpret instructions for data handling inaccordance with specified logic and algorithms can be used to performthe microprocessor functions.

An example of a microprocessor that also incorporates an USB SerialInterface Engine supporting all three USB speeds, low-, full- andhigh-speed, is the EZ-USB FX2LP™ available from Cypress SemiconductorCorporation. An example of a microprocessor that also incorporates anUSB Serial Interface Engine supporting two USB speeds, low- andfull-speed, is the AT89C5130A-M available from Atmel Corporation.Examples of USB high-speed hubs are the ISP1520 with four downstreamports and the ISP1521 with seven downstream ports, both available fromPhilips Semiconductors.

In accordance with an embodiment of the present invention, a system forenhancing universal serial bus (USB) applications comprises an upstreamprocessor, a downstream processor and a main controller. The upstreamprocessor accepts standard USB signals from a USB host and independentlyprovides responses required by USB specification within the requiredtime frame. The downstream processor connectable to USB-compliantdevices accepts the USB signals from the USB-compliant devices andprovides responses required by USB specification within the requiredtime frame. The main controller interconnects the upstream anddownstream processors, and provides timing independence between upstreamand downstream timing.

In accordance with another embodiment of the present invention, a systemfor enhancing universal serial bus (USB) applications comprises anupstream processor, a downstream processor and a main controller. Theupstream processor accepts standard USB signals from a USB host andindependently provides responses required by USB specification withinthe required time frame. It also contains storage for descriptors for adevice associated with this upstream processor. The main controllerobtains the descriptors by commanding the downstream processor, andpasses them to the upstream processor. The downstream processorconnectable to USB-compliant devices accepts the USB signals from theUSB-compliant devices and provides responses required by USBspecification within the required time frame. The main controllerinterconnects the upstream and downstream processors, and providestiming independence between upstream and downstream timing. It alsocommands the downstream processor to obtain device descriptorsindependent of the host.

In accordance with another embodiment of the present invention, a systemfor enhancing universal serial bus (USB) applications comprises anupstream processor, a downstream processor and a main controller. Theupstream processor accepts standard USB signals from a USB host andindependently provides responses required by USB specification withinthe required time frame. The downstream processor connectable toUSB-compliant devices accepts the USB signals from the USB-compliantdevices and provides responses required by USB specification within therequired time frame. The main controller interconnects the upstream anddownstream processors, and provides timing independence between upstreamand downstream timing. It also commands the downstream processor toobtain device descriptors independent of the host, and stores them forsupplying them to the upstream processor.

In accordance with an embodiment of the present invention, a method forenhancing universal serial (USB) applications comprises the steps ofaccepting standard USB signals from a USB host by an upstream processorand independently providing responses in conformance with USBspecification, accepting the USB signals from USB-compliant devices by adownstream processor and providing responses in conformance with USBspecification, and interconnecting the upstream and downstreamprocessors while providing timing independence between upstream anddownstream timing.

In accordance with another embodiment of the present invention, a methodfor enhancing universal serial (USB) applications comprises the steps ofaccepting standard USB signals from a USB host by an upstream processorand independently providing responses in conformance with USBspecification, accepting the USB signals from USB-compliant devices by adownstream processor and providing responses in conformance with USBspecification, independently obtaining device descriptors and storingthem and supplying the descriptors to the host upon request, andinterconnecting the upstream and downstream processors while providingtiming independence between upstream and downstream timing.

In accordance with an embodiment of the present invention, a computerreadable medium comprising code for enhancing universal serial (USB)applications. The code comprising instructions for accepting standardUSB signals from a USB host by an upstream processor and independentlyproviding responses in conformance with USB specification, accepting theUSB signals from USB-compliant devices by a downstream processor andproviding responses in conformance with USB specification, andinterconnecting the upstream and downstream processors while providingtiming independence between upstream and downstream timing.

In accordance with another embodiment of the present invention, acomputer readable medium comprising code for enhancing universal serial(USB) applications. The code comprising instructions for acceptingstandard USB signals from a USB host by an upstream processor andindependently providing responses in conformance with USB specification,accepting the USB signals from USB-compliant devices by a downstreamprocessor and providing responses in conformance with USB specification,independently obtaining device descriptors and storing them andsupplying the descriptors to the host upon request, and interconnectingthe upstream and downstream processors while providing timingindependence between upstream and downstream timing.

Various other objects, advantages and features of the present inventionwill become readily apparent from the ensuing detailed description, andthe novel features will be particularly pointed out in the appendedclaims.

BRIEF DESCRIPTION OF THE DRAWINGS

The following detailed description, given by way of example and notintended to limit the present invention solely thereto, will best beunderstood in conjunction with the accompanying drawings in which:

FIG. 1 is a block diagram of a system in accordance with an embodimentof the present invention;

FIG. 1A is a block diagram of a system in accordance with an embodimentof the present invention;

FIG. 1B is a block diagram of a system in accordance with an embodimentof the present invention showing independent time bases;

FIG. 2 is a block diagram of the Upstream Processor in accordance withan embodiment of the present invention;

FIG. 2A is a block diagram of the Upstream Processor in accordance withanother embodiment of the present invention;

FIG. 3 is a block diagram of the Downstream Processor in accordance withan embodiment of the present invention;

FIG. 4 is a block diagram of the Main Controller in accordance with anembodiment of the present invention;

FIG. 4A is a block diagram of the Main Controller in accordance withanother embodiment of the present invention;

FIG. 5 is a signal diagram of a Downstream to Upstream transfer inaccordance with an embodiment of the present invention;

FIG. 6 is a sequence diagram of a Control Read transfer in accordancewith an embodiment of the present invention;

FIG. 6A is a sequence diagram of a high speed Bulk Out transfer inaccordance with an embodiment of the present invention;

FIG. 7 (a)-(d) are diagrams of the data structures of AttachmentTopology Management in accordance with an embodiment of the presentinvention;

FIG. 8 (a)-(e) are diagram of an example of the use of the datastructures of Attachment Topology Management in accordance with anembodiment of the present invention;

FIG. 9 is a diagram of the major processes in accordance with anembodiment of the present invention;

FIG. 10 is a diagram of the processes of the US Process in accordancewith an embodiment of the present invention;

FIG. 10A is a diagram of the processes of the US Process in accordancewith another embodiment of the present invention;

FIG. 11 is a diagram of the processes of the DS Process in accordancewith an embodiment of the present invention;

FIG. 12 is a diagram of the processes of the Main Process in accordancewith an embodiment of the present invention; and

FIG. 12A is a diagram of the processes of the Main Process in accordancewith an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED

The following detailed description sets forth numerous specific detailsto provide a thorough understanding of the invention. However, thoseskilled in the art will appreciate that the invention may be practicedwithout these specific details. In other instances, well known methods,procedures, components, and circuits have not been described in detailso as not to obscure the invention.

Turning now to FIG. 1, there is illustrated a system in accordance withan embodiment of the present invention. A number of Upstream (US)Processors (11) connect to USB hosts via USB signals (21) and (22). USBsignals to each USB host are individual for that host. The US Processors(11) also connect to the Main Controller (10) via US Interconnect (25).A number of Downstream (DS) Processors (12) provide connection to anumber of USB-compatible devices via USB signals (23) and (24). USBsignals to each USB-compatible device are individual for that device.The DS Processors (12) also connect to the Main Controller (10) via DSInterconnect (26). The Main Controller (10) analyzes, processes andbidirectionally routes information between the US Processors (11) andthe DS Processors (12). The Main Controller (10) also provides timedecoupling between the US and DS sides. It will be understood by oneskilled in the art that the number of US Processors (11) and the numberof DS Processors (12) can be more or less than the number shown in FIG.1.

To allow a group of USB devices to be connected to the same host,standard USB hubs can be incorporated into the system in accordance withan embodiment of the present invention as shown in FIG. 1A. FIG. 1Ashows the hubs (15) grouping several Upstream Processors (11) into onephysical connection to an USB host. The hubs connect to USB hosts viaUSB signals (21) and (22). USB signals to each USB host are individualfor that host. US Processors (11) connect to hubs (15) via USB signals(27), (28), (29) and (30). It will be understood by one skilled in theart that the number of US Processors (11) connecting to each hub (15)and the number of hubs (15) can be more or less than the number shown inFIG. 1A.

Referring to FIG. 1, on initial power-up, the US Processors (11) assertthe SE0 state on their USB data lines, indicating that no device isconnected. The DS processors (12) begin to examine the state of theirUSB lines for indication that a peripheral is connected. When a deviceor hub is attached to a DS processor (12), an examination is performedto determine the class of peripheral that was attached, and to obtainbasic data about the peripheral. If a hub has been attached, it isenumerated, an address is assigned, and periodic status requests arestarted to determine if a peripheral is attached to one of the hub'sports. When it is determined that a peripheral has been attached to oneof the ports, the examination is repeated. This process continues untilthe USB specification limit of hubs connected in series to one anotherhas been reached or until a device is attached. Similar to hubs, anexamination of the device is performed to obtain basic data about thedevice, including its speed, and an address is assigned to the device.At this point, the Main Controller (10) looks up the identification ofthe US Processor (11) to which this particular DS Processor (12), andthereby the USB device just attached, should be connected. Theconnection between downstream and upstream is usually specified by auser of the invention via User Inputs signals (16), but can be specifiedby other means as will be apparent to one skilled in the art. The MainController (10) maintains the specified connections in a Connection Map(65), in FIG. 4. The Main Controller (10) looks up the proper USProcessor (11) and if an USB host is present, the Main Controllercommands the US Processor (10) to signal plug-in and speed by removingthe SE0 state from the USB data lines by making the D+ line positive forfull or high speed devices, or the D− line positive for low speeddevices. Removing the SE0 state indicates attachment of a device causingthe host to initiate its enumeration process.

When the US Processor (11) detects an USB reset signal and has beenconditioned by the Main Processor (10) to respond as a high speeddevice, it will issue a high-speed Chirp K signal. If the host or theupstream hub to which the US Processor (11) is connected, is high speedcapable, it detects this signal and initiates its high-speed chirpsequence of alternating Chirp J and Chirp K, in accordance with USBSpecification paragraphs 7.1.5 and 7.1.7, to indicate that it ishigh-speed capable. If the US Processor (11) does not see the responsefrom the host as given above, it remains in full speed mode. After thenegotiation about speed, the USB host will issue a sequence of ControlTransfers, called enumeration, to establish the capabilities of theattached device. Responses to host transmissions have to meet tight USBspecification timing requirements. These responses are supplied by theUS Processor (11) within the USB Specification time constraints, and notby the actual device connected to the DS Processor (12), therebydecoupling time-wise the actual device from the host, and allowing theenhancements to USB applications of the invention to be implemented.With reference to FIG. 5, which illustrates time decoupling between thehost (upstream) and device (downstream), after the DS Processor (12)detects attachment of a device, it initiates SOF's every 125microseconds if the device is high speed, every millisecond if thedevice is full speed or an EOP signal every millisecond if the device islow speed, establishing Time Base 2 (211). When the USB host detects theremoval of the SE0 state from the upstream USB data lines by the USProcessor (10), indicating attachment, the USB host initiates SOF'severy 125 microseconds if the US Processor (10) signaled high speed,every millisecond if full speed or an EOP signal every millisecond iflow speed, establishing Time Base 1 (210). Time Base 1 (210) isindependent from Time Base 2 (211). When a packet (201) is received bythe US Processor (11), the US Processor (11) is able to provide theappropriate response within the timing specifications of the USBspecification irrespective of communication time between the USProcessor (11), the DS Processor (12) and the device. If the packet is atoken of the type IN, requesting data from the device, the US Processor(11) either provides data if it has the data or a NAK response if itdoes not have data, in either case satisfying the host. The US Processor(11) also signals the DS Processor (12) via signal (203) that it hasreceived a packet from the host directed at the device. Signal (203)contains information about the type of packet that was received by theUS Processor (10). The communications method used for signal (203) canbe the most suitable for the intended application, and can include fiberoptic communications, Ethernet, TCP/IP, and other methods suitable forsignificant distance separation between the US Processor (11) and theMain Controller (10), and local bus interface circuitry. FIG. 5 omitsthe Main Controller (10) for clarity. When the DS Processor (12)receives signal (203), it reformats the packet into USB signals andsends it to the device. The device response (205) can be data, if thepacket was a token of the type IN. The DS Processor (12) then sends thereceived data via signal (203) to the US Processor (11). The dataprovided by the actual device is now available for transmission to thehost at the next request for data by the host.

The method of time decoupling and supplying true device enumeration datawhich provides the enhancements to USB applications by the currentinvention is further detailed in FIG. 6, which illustrates a ControlRead transfer type as practiced by the invention. When the US Processor(11) receives a Setup request (101) from the host, it decodes the packetas a Setup-type packet and makes itself ready to accept the followingdata packet (102). Details of the US Processor (11) are shown in FIG. 2and are presented later. The US processor (11) issues a handshake signal(103), ACK as required by the USB specification and within the timingrequirements of the USB Specification. The US processor (11) notifiesthe Main Controller (10) via signal (130) that the Setup packet and itsdata have been received. The Main Controller (10) acquires the data ofthe Setup packet from the US Processor (11) via signal (130) and sendsit to the DS processor (12) via signal (131), indicating that this is aSetup packet and the specifics of the Setup packet. The DS Processor(12) sends a Setup packet (121) and its data (122) to the device via USBsignaling. The device sends an ACK response (123) within the timerequired by the USB Specification. FIG. 6 shows that the communicationsbetween the host and the US Processor (11) and between the DS Processor(12) and the device follow different time bases, Time Base 1 (210) forcommunications between host and US Processor (11) and Time Base 2 (211)for communications between DS Processor (12) and device. The two timebases are independent. In a Control Read transfer type the host followsthe Setup and its data packet with an IN request (104). The time betweenthe host receiving the handshake ACK (103) and sending the IN (104)depends on the particular host and is not specified in the USBSpecification. The US Processor (11) responds with a NAK (105)handshake, since it has not yet received data from the device, to the INrequest (104) from the host within the timing requirements of the USBSpecification. After the DS Processor (12) has received the ACK (123)from the device, it notifies the Main Controller (10) via signal (132).The Main Controller (10), having interpreted the Setup packet receivedvia signal (130) as a Control Read, commands the DS Processor (12) viasignal (133) to issue an IN request (124) to the device. The device willrespond with a data packet (125), assuming the device is ready to senddata, within the timing requirements of the USB Specification. If thedevice is not ready, it will respond with a NAK. The DS Processor (12)will repeat sending the IN request (124) to the device until it receivesdata. The DS Processor (12) receives the data packet (125) from thedevice, sends an ACK (126) handshake to the device within the timingrequirements of the USB Specification, and sends the data from thedevice to the Main Controller (10) via signal (134). The Main Controller(10) presents the data to the US Processor (11) via signal (135). The USProcessor (11) marks that it has data and on the next IN request (106)from the host sends a data packet (107) to the host, the said datapacket containing the data obtained from the device by the DS Processor(12) from the data (125) sent by the device. Thereby the host receivesdata obtained from the actual device within the timing requirements ofthe USB specification on the host side. After receiving the data (107)from the US Processor (11) the host sends an ACK (108) handshake to theUS Processor (11). Assuming that the Control Read transfer type used toillustrate the method of time decoupling of the invention, and shown inFIG. 6, requires one data packet, the host will initiate the Statusstage of the Control Read transfer by sending an OUT packet (109) to theUS Processor (11) followed by a zero-length data packet (110). The timebetween the host sending the handshake ACK (108) and sending the OUT(109) depends on the particular host and is not specified in the USBSpecification. The US processor (11) receives the OUT (109) packet andthe zero-length data packet (110) and issues a handshake signal (111),NAK, within the timing requirements of the USB Specification, indicatingto the host that it is not yet ready to reply to the Status stage. TheUS Processor (11) notifies the Main Controller (10) via signal (136)that the host has initiated the Status stage of the Control Readtransfer. The Main Controller (10) commands the DS Processor (12) viasignal (137) to initiate the Status stage of the Control Read transferon the device side. The DS Processor (12) issues an OUT packet (127) tothe device followed by a zero-length data packet (128). The devicereceives the OUT (127) packet and the zero-length data packet (129) andissues a handshake signal (129), ACK in the case when both the Setup anddata packets were received correctly by the device and the Setup requestwas supported by the device, within the timing requirements of the USBSpecification on the device side, thereby terminating the Control Readtransfer on the device side. The DS Processor (12) notifies the MainController (10) via signal (138) that an ACK was received from thedevice, and the Main Controller (10) notifies the US Processor (11) viasignal (139). The host issues another OUT (112) packet followed by azero-length data packet (113). The US processor (11) receives the OUT(112) packet and the zero-length data packet (113) and issues ahandshake signal (114), ACK, thereby terminating the Control Readtransfer on the host side.

The method of time decoupling which provides the enhancements to USBapplications by the current invention is additionally detailed in FIG.6A, which illustrates a high speed Bulk Out transfer type, consisting oftwo data packet transmissions, as practiced by the invention. When theUS Processor (11) receives a Ping packet (151) from the host, it decodesthe packet as a Ping packet and checks its buffers for available space.Details of the US Processor (11) are shown in FIG. 2 and are presentedlater. In the example of FIG. 6A, space is available and the USprocessor (11) issues an ACK handshake signal (152) within the timingrequirements of the USB Specification. The US processor (11) notifiesthe Main Controller (10) via signal (180) that a Ping packet has beenreceived. The Main Controller (10) notifies the DS processor (12) viasignal (184) to issue a Ping packet to the device. The DS Processor (12)issues a Ping packet (161) to the device via USB signaling. The devicesends an ACK response (162) within the time required by the USBSpecification given that it has space for Bulk Out data. FIG. 6A showsthat the communications between the host and the US Processor (11) andbetween the DS Processor (12) and the device follow different timebases, Time Base 1 (210) for communications between host and USProcessor (11) and Time Base 2 (211) for communications between DSProcessor (12) and device. The two time bases are independent. In a highspeed Bulk Out transfer type the host follows the Ping packet with anOUT packet (153) and a data packet (154). The time between the hostreceiving the handshake ACK (152) and sending the OUT (153) depends onthe particular host and is not specified in the USB Specification. TheUS Processor (11) responds with a NYET (155) handshake to the OUT—datatransmission sequence from the host within the timing requirements ofthe USB Specification. The US processor (11) notifies the MainController (10) via signal (181) that Out data has been received. TheMain Controller (10) sends the Out data to the DS processor (12) viasignal (186). The Main Controller (10) has been notified by the DSProcessor (12) via signal (185) that the device has responded with anACK to a Ping inquiry, indicating it is ready to accept Out data. Whenthe DS Processor (12) receives the Out data via signal (181), it issuesto the device an OUT packet (163) followed by a data packet (164) viaUSB signaling. The device sends a NYET response (165) within the timerequired by the USB Specification indicating that it received the datacorrectly, but is not yet ready to accept another data packet. After theDS Processor (12) has received the NYET (165) from the device, itnotifies the Main Controller (10) via signal (187). The Main Controllerrecords that a NYET (165) has been received from the device. The host,having received a NYET handshake (155) to its previous OUT packet (153)and data packet (154), issues a Ping packet (156). The US Processor (11)decodes the packet as a Ping packet and since space is available issuesan ACK handshake signal (157) within the timing requirements of the USBSpecification. The US processor (11) notifies the Main Controller (10)via signal (182) that a Ping packet has been received. The MainController (10) notifies the DS processor (12) via signal (188) to issuea Ping packet to the device. The DS Processor (12) issues a Ping packet(166) to the device via USB signaling. The device sends an ACK response(167) within the time required by the USB Specification given that ithas space for Bulk Out data. The DS Processor (12) notifies the MainController (10) via signal (189) that the device is ready to accept moredata. The host, having received an ACK handshake (157) to its Pinginquiry (156) sends the second OUT packet (158) followed by a datapacket (159). The time between the host receiving the handshake ACK(157) and sending the OUT (158) depends on the particular host and isnot specified in the USB Specification. The US Processor (11) respondswith a NYET (160) handshake to the OUT-data transmission sequence fromthe host within the timing requirements of the USB Specification. TheBulk Out transfer is now completed. The US processor (11) notifies theMain Controller (10) via signal (183) that Out data has been received.The Main Controller (10) sends the Out data to the DS processor (12) viasignal (190). The Main Controller (10) has been notified by the DSProcessor (12) via signal (189) that the device has responded with anACK to a Ping inquiry, indicating it is ready to accept Out data. Whenthe DS Processor (12) receives the Out data via signal (190), it issuesto the device an OUT packet (168) followed by a data packet (169) viaUSB signaling. The device sends a NYET response (170) within the timerequired by the USB Specification indicating that it received the datacorrectly, but is not yet ready to accept another data packet. After theDS Processor (12) has received the NYET (170) from the device, itnotifies the Main Controller (10) via signal (191). The Main Controllerrecords that a NYET (191) has been received from the device. Thisexample considered the case where the Bulk Out data transfer consists oftwo data packets. Therefore, after receiving the NYET (160) handshake,which indicates that data was received correctly, from US Processor (11)the host has satisfactorily completed the high speed Bulk Out transferand further communications from the host are for other transfers.

Upstream and downstream timing independence and passing true deviceenumeration data to the host as practiced by the invention, and asdemonstrated by the examples in FIG. 6 and FIG. 6A, applies among allthe US Processors (11) and the DS Processors (12). Referring to FIG. 1B,USB signals (21) of US Processor (11) #1 are on Time Base 1 (31). USBsignals (22) of US Processor (11) #N are on Time Base N (32). USBsignals (23) of DS Processor (11) #1 are on Time Base N+1 (33), and USBsignals (24) of DS Processor (11) #M are on Time Base N+M (34). Timebases 1 (31), N (32), N+1 (33) and M (34) are all independent from eachother. There are thus N+M independent time bases. It will be understoodby one skilled in the art that the number of independent time basesdepends on the number of US Processors (11) and the number of DSProcessors (12) and can be more or less than the number shown in FIG.1B.

FIG. 2 is a detailed a block diagram of the US Processor (11) inaccordance with an embodiment of the present invention. The SerialInterface Engine (SIE) (41) receives and generates USB signals (46) fromand to an USB host. The SIE (41) converts received USB signals (46) to aform used within the US Processor (11). The SIE (41) also generates USBsignals (46) to the USB host, converting from form used within the USProcessor (11) to USB signaling form. Once a packet has been receivedfrom the host, the SIE (41) records the packet and the data, if any isassociated with the packet, in the Payload and Command Buffer (PCB) (43)and advises the Control Logic (40). Control Logic (40) sends theinformation in the PCB (43) to the Main Controller (10) viaDrivers/Receivers (45) and US Interconnect (25). One skilled in the artwill appreciate that the Drivers/Receivers (45) and US Interconnect (25)are optimized for particular communications methods with the MainController (10), which can include fiber optic communications, Ethernet,TCP/IP, and other methods suitable for significant distance separationbetween the US Processor (11) and the Main Controller (10), and caninclude local bus interface circuitry. The SIE (41) generates handshakesignals required by the USB Specification to stay within the timingrequirements of the USB Specification. The SIE (41) uses informationfrom the Handshake Control (HC) (44) to determine the type of handshakesignal to generate if the packets received from the host are not inerror. If the packets are in error, the SIE (41) does not place thereceived data in the PCB (43) and does not advise the Control Logic (40)that a packet was received. It also does not generate a handshakeresponse. If Control Logic (40) has placed valid data in the PCB (43) itconditions the HC (44) to indicate to the SIE (41) to send the data ifan IN packet for the endpoint is received from the USB host. ControlLogic (40) also independently manages data toggle synchronizationinsuring correct data transmission to the USB host. If there is no validdata in the PCB (43), the HC (44) indicates to the SIE (41) to respondwith a NAK signal. The Control Logic (40) coordinates data and commandcommunications with the Main Controller (10) via the Drivers/Receivers(DR) (45). The Control Logic (40) also coordinates handshake generationand evaluation using information received from the Main Controller (10),the SIE (41) and information contained in the PCB (43). Speed Signalingand Control (SSC) (42) controls special states of the USB signals (46).After initial power-up, SSC (42) signals state SE0 on the USB signals(46), indicating that no device is attached to the host. When commandedby the Main Controller (10), via signals received through the DR (45)and Control Logic (40), SSC (42) removes the SE0 state from the USBsignals (46) and signals the speed commanded by the Main Controller (10)by connecting either the D− or D+ line to a positive voltage. In thecase the Main Controller (10) has commanded high speed, the SSC (42)looks for the USB reset signal on the USB signal lines (46). When thissignal is detected by SSC (42), it starts the Chirp K sequence specifiedby the USB specification to indicate that it is a high speed device andto determine if the host supports high speed. If the host answers with aChirp K, Chirp J sequence, as specified in USB Specification paragraphs7.1.5 and 7.1.7, SSC (42) informs Control Logic (40) that a high speedhost is present. Control Logic (40) in turn informs the Main Controller(10) via the DR (45) that a high speed host is present. If SSC (42) doesnot receive the proper Chirp K, Chirp J sequence in response, it remainsa full speed device, and informs Control Logic (40) that a high speedhost is not present. Control Logic (40) in turn informs the MainController (10) via the DR (45) and US Interconnect (25) that a highspeed host is not present. SSC (42) monitors the USB signal lines (46)for the presence of bus activity, indicated by SOF or EOP signals. Ifthese signals are not present, SSC (42) informs Control Logic (40) thatbus activity is not present. Control Logic (40) in turn informs the MainController (10) via DR (45) that bus activity is not present. When busactivity resumes, SSC (42) detects the resumption and informs the MainController (10) via Control Logic (40) and DR (45). SSC (42) alsocontrols the SIE (41) to issue resume signaling when commanded byControl Logic (40). Control Logic (40) in each US Processor (11)autonomously coordinates actions of the circuits comprising each USProcessor (11) using information received from the Main Controller (10)as needed, thereby providing timing independence from other USProcessors (11) and from DS Processors (12).

FIG. 2A is a detailed block diagram of the US Processor (11) inaccordance with another embodiment of the present invention allowingunlimited distance separation between USB host(s) and USB device(s)while supplying true device enumeration data to the host. Thisembodiment contains all functions of the embodiment shown in FIG. 2. Inaddition, it contains a Descriptors Buffer (DB) (46). The DB (46) storesUSB descriptors obtained by the DS Processor (12) from a USB deviceassociated with this US Processor (11). The descriptors are obtained bythe Main Controller (10) before device attachment is signaled to thehost by removal of SE0 state. Thus, when device attach is signaled tothe USB host as described above, and the USB host begins the deviceenumeration sequence, the requests for descriptors are not passed to theDS Processor (12), but are fulfilled from the information in the DB(46).

FIG. 3 is a detailed a block diagram of the DS Processor (12) inaccordance with an embodiment of the present invention. The SerialInterface Engine (SIE) (51) receives and generates USB signaling (55)from and to the device. The SIE (51) converts received USB signals (55)to a form used within the DS Processor (12). The SIE (51) also generatesUSB signals (55) to the device, converting from form used within the DSProcessor (12). Once a packet has been received from the device, the SIE(51) records the packet in the Data and Command Buffer (DCB) (53),places the data, if any is associated with the packet in the DCB (53)and advises Control Logic (50). Control Logic (50) sends the informationin the DCB (53) to the Main Controller (10) via Drivers/Receivers (54)and DS Interconnect (26). One skilled in the art will appreciate thatthe Drivers/Receivers (54) and DS Interconnect (26) are optimized forparticular communications methods with the Main Controller (10), whichcan include such methods as fiber optic communications, Ethernet,TCP/IP, and other methods suitable for significant distance separationbetween the DS Processor (12) and the Main Controller (10), and caninclude local bus interface circuitry. The SIE (51) also generateshandshake signals to the device required by the USB Specification withinthe timing requirements of the USB Specification. The Control Logic (50)coordinates data and command communications with the Main Controller(10) via the Drivers/Receivers (DR) (54) and DS Interconnect (26). Afterinitial power-up, Control Logic (50) checks the state of USB signals(55) as detected by the SIE (51). If no peripheral is attached, the SE0state exists on the USB signals (55). When a peripheral is attached tothe USB signals (55), the SE0 state changes in accordance with the speedof the attached peripheral, with the D− line assuming a positive voltageif a low speed peripheral has been attached and the D+ line assuming apositive voltage if a full or high speed peripheral has been attached.If attachment of a full speed peripheral is indicated, Control Logic(50) commands the SIE (51) to issue an USB reset signal on the USBsignal lines (55). When this signal is detected by a high speedperipheral, it starts the Chirp K sequence specified by the USBspecification in paragraphs 7.1.5 and 7.1.7 to indicate that it is ahigh speed device. If the SIE (51) signals the Control Logic (50) thatthe Chirp K sequence has been detected on the USB signal lines (55),Control Logic (50) commands the SIE (51) to answer with a Chirp K, ChirpJ sequence. If the Chirp K sequence is not detected by the SIE (51) inresponse to the USB reset signal, it indicates that a full speed devicehas been attached. Control Logic (50) informs the Main Controller (10)via the DR (54) that a peripheral has been attached and the speed of theperipheral. Control Logic (50) commands the Timing Generator (TG) (52)to start SOF or EOP signals in accordance with the speed of the attachedperipheral. If the attached peripheral is high speed, SOF's aregenerated every 125 microseconds, each SOF defining the beginning of amicro-frame. If the attached peripheral is full speed, SOF's aregenerated every millisecond. If the attached peripheral is low speed, anEOP signal is generated every millisecond. Timing Generators (52) ineach DS Processor (12) autonomously maintain frame or micro-frame timingon the USB signals (55) providing a time base independent from other DSProcessors (12) and from US Processors (11). Control Logic (50) usesTiming Generator (52) to check that no babble condition exists on USBsignals (55). Control Logic (50) also uses Timing Generator (52) to timemanage information to and from attached devices by using maximum payloadinformation of the device, or length of data intended for the device, tocalculate if there is enough time for the complete transfer in thecurrent frame, or microframe if the recipient device is high speed. Ifthere is not, the transfer is delayed until the next frame ormicroframe. After the speed of the attached peripheral has beendetermined, the Main Controller (10) commands Control Logic (50) via DR(54) to perform a partial enumeration to obtain basic information aboutthe attached peripheral, such as whether it is a hub or not, and themaximum payload of the device. Further details of this process areprovided in the description of the Main Controller (10). At theconclusion of this process the Main Controller (10) has determined ifthe attached peripheral is a hub or a device. When a peripheral isdetached, USB signals (55) assume the SE0 state. When Control Logic (50)detects that the SIE (51) has found the SE0 state, indicating peripheraldetachment, it informs the Main Controller (10) via DR (54) that adetach event has occurred at this DS Processor (12). The Main Controller(10) processes the detach event as presented in the description of theMain Controller (10). The Main Controller (10) also monitors Controltransfers from the US Processor (11) directed to the DS Processor (12).If an USB host issues a command enabling the Remote Wakeup Feature, itis noted by the Main Processor (10). When subsequently US Processor (11)reports Loss Of Activity, the Main Processor (10) commands the DSProcessor (12) to stop generation of the frame timing signals to the USBdevice. Control Logic (50) commands Timing Generator (52) to stopgeneration of the frame timing signals to the USB device. The SIE (51)continues to monitor the state of the USB signals (55) and advisesControl Logic (50) when resume signaling is detected. Control Logic (50)passes this information to the Main Processor (10) via DR (54). The MainProcessor (10) then commands the US Processor (10) to issue resumesignaling on its USB signals (46).

The Main Controller (10), shown in FIG. 4, coordinates US Processors(11) and DS Processors (12), which are all operating on independent timebases, routes information bidirectionally among the DS Processors (12)and US Processors (11), maintains information about the attachmenttopology of hubs and devices attached to the DS Processors, and providesfacilities for user control and indications. Execution Control Logic(ECL) (69) controls and coordinates other functional components of theMain Controller (10). The Display Drivers (70) perform electrical signaladaptation to match characteristics of a particular display and generateSystem Indication (17) signals under control of Display Control (68).Display Control (68) derives information from the Connection Map (CM)(65) and from ECL (69). User Inputs (16) are adapted by Input Receivers(60) and further processed by User Interface (67). One of the functionsavailable via the User Interface (67) is switching of devices to hosts.User Interface (67) modifies the CM (65), causing ECL (69) to initiaterequired switching actions. ECL (69) advises Routing Control (64) of achange in CM (65). CM (65) contains current connection information,relating DS Processors (12) to US Processors (11), and informationlocking out connection to certain US Processors (11), effectivelydeclaring these US Processors (11) “busy”. The “busy” condition may beestablished dynamically, and may be removed dynamically, among othermeans, by User Inputs (16), data activity by DS Processors (12) or byother appropriate means. Routing Control (64) uses information in the CM(65), translates it into physical addressing information and directsinformation flow from/to US Processors (11) and DS Processors (12). Inaddition to using information in the CM (65), Routing Control (64)examines messages stored in the Data and Command Buffers (DCB) (66) todetermine the source, type and content of the messages. Given thesource, the information in the CM (65) permits look-up of thedestination, or destinations, for the message. Routing Control (64) alsoremaps device addresses assigned by an USB host, as reported by an USProcessor (11), to device addresses assigned to a device by ECL (69). Toprevent message misrouting, ECL (69) changes CM(65) data only when DCB(66) is empty. CL (62) manages the protocol layer of communications withthe US Processors (11) and DS Processors (12) via US Interconnect (25)and DS Interconnect (26) by controlling the US Drivers/Receivers (61)and the DS Drivers/Receivers (62). In addition to providing thesignaling and electrical layer of communications with the US Processors(11) and the DS Processors (12) via US Interconnect (25) and DSInterconnect (26), the US Drivers/Receivers (61) and the DSDrivers/Receivers (62) adapt the signals between the Main Controller(10) and US Interconnect (25) and DS Interconnect (26). A practitionerof ordinary skill in the art will understand that the signals to USInterconnect (25) and DS Interconnect (26) and from US Interconnect (25)and DS Interconnect (26) to the US Processors (11) and the DS Processors(12) may be different from each other in nature, and that they may be ofthe same nature as the signal levels used by the Main Controller (10).Communications methods can include fiber optic communications, Ethernet,TCP/IP, and other methods suitable for significant distance separationbetween the US Processors (11), US Interconnect (25), the Main Processor(10), DS Interconnect (26), and the DS Processors (12), and may includelocal bus interface circuitry. US Interconnect (25) and DS Interconnect(26) include functionality to select one or more US Processor (11) andone or more DS Processor (12) as a source or destination of informationflow between the Main Controller (10) and US Processors (11) and DSProcessors (12). In a particular embodiment, US Interconnect (25) and DSInterconnect (26) can be a conventional parallel or serial bus, or canbe an arrangement to allow connection separation between the MainController (10) and US Interconnect (25) and DS Interconnect (26). Theparticular embodiment for US Interconnect (25) can be different from orcan be the same as the DS Interconnect (26).

FIG. 4A shows an embodiment of the Main Controller (10) that allowsunlimited separation distance between an USB host and an USB device,while supplying true enumeration data from a device. The Main Controller(10) in this embodiment contains all functions of the embodiment shownin FIG. 4 and described above. In addition, it contains a DescriptorsBuffer (DB) (71). The DB (71) stores USB descriptors obtained by the DSProcessor (12) from a US device upon commands from the Main Controller.ECL (69) in this embodiment commands the DS Processor (12) to perform acomplete enumeration of the USB device, obtaining all standard and classdescriptors specified in the USB Specification. The descriptors aresupplied to the USB host via the US processor (11) in response todescriptor requests issued by the USB host.

After a DS Processor (12) has detected attachment of a peripheral, itreports the event and the speed of the attached peripheral to the MainController (10), which commands the DS Processor (12) to perform apartial enumeration to obtain basic information about the attachedperipheral, including, but not limited to, whether it is a hub or not,and the maximum payload of the device. If the peripheral is device, ECL(69) uses information in the CM (65) to determine the US Processor (11)to which this device should be attached and commands the US Processor(11) to signal device attachment on its USB signals (46). If theperipheral is a hub, Attachment Topology Management (ATM) (63) datastructures are updated. Downstream hub attachment is not reflectedupstream, thereby allowing the full configuration of five hubs in serieson the upstream, USB host, side. ATM (63) receives and processes reportsof peripheral attachment and detachment reported by the DS Processors(12). ATM (63) manages information about the topology of downstream huband device connections and the addresses of each device and hub. Thecurrent downstream attachment topology and address assignment are heldin data structures unique for each DS Processor (12) and in global datastructures. The information for these data structures is derived in partfrom reports by DS Processors (12) about peripheral attachment anddetachment. The ATM (63) data structures are illustrated in FIGS. 7(a)-(d). The data structures comprises of three types: a) global, whichapply to all DS Processors (12), shown in FIG. 7 (a) and (b); b)group-oriented, which apply to a group of DS Processors (12), shown inFIG. 7 (c); c) individual, which apply to one DS Processor (12), shownin FIG. 7 (e). There is one set of global data structures. The number ofgroup-oriented data structures equals the number of groups, which mayequal one or more. The number of individual data structures equals thenumber of DS Processors (12), which may equal one or more. Global datastructures are Group Definition (301) and Group List (304), shown inFIG. 7 (a) and (b) respectively. Group Definition (301) specifies thenumber of DS Processors (12) in a group in group_size (302), which mayequal one or more, and the number of groups in no_groups (303), whichalso may equal one or more. The Group List (304) specifies which DSProcessors (12) is part of one group. The Group List (304) contains anumber of lists equal to the number of groups, specified in no_groups(303). Each list contains identifications of the DS Processors (12)constituting a group. The Device Control (305), FIG. 7 (c), datastructure contains an element, devices_left_j (317) for each group.Device Control (305) controls the number of devices that can be attachedto the DS Processors (12) in one group. Device Control (305) isinitialized to group_size (302) on start-up. Each element,devices_left_j (317), is dynamically controlled as devices are attachedand detached. There is one set each of the data structure next_address(306) and the Peripheral_Definition_List (PDL) (307), FIG. 7 (d), foreach DS Processor (12). The PDL (307) entries p_address (310), p_class(311), p_speed (312), higher_hub_address (313), port_no (314), andno_of_ports (315) form one element of the PDL (307). Each elementdefines one attached peripheral, hub or device. The number of elementsdynamically increases and decreases during operation as devices and hubsare attached and detached. The next_address (306) is initialized onpower-up to one and is incremented as hubs and devices are attached. Itis reset to one when all peripherals have been detached from the DSProcessor (12) to whom the next_address (306) data structure applies.

The USB specification handles transmission or signaling errors byrequiring that the recipient of a transmission in error not respond witha handshake, except for isochronous transfers, which have no handshakerequirement. Absence of a response in time is an indication of error.This type of error can occur at the US Processors (11) or the DSProcessors (12). If a US Processor (11) receives a corrupted hosttransmission, it does not respond, thereby signaling an erroneousreception, and does not pass on the error to the Main Controller (10),isolating the error. The USB host handles the error in the manner it maybe programmed. If a US Processor (11) does not receive a requiredhandshake from its USB host, it waits for action from the host. The MainController (10) is notified that the transfer was not completed, and ofactions taken by the host. If the DS Processor (12) does not receive aresponse in time for a transmission to a peripheral, it retries therequest three times, and reports to the Main Controller (10) if it isnot successful. The Main Controller (10) commands the US Processor (11),which is connected to the DS Processor (12) not to respond to furtherhost requests, thereby passing on the device error.

The USB specification also requires all USB-compatible devices tosupport certain Setup requests from the USB host. Other Setup requests,including Setup requests specified by a USB device vendor, are notrequired to be supported. If an USB-compliant device receives such anunsupported request, it must reply with a STALL handshake. The STALLresponse is usually given by an USB-compliant device in the Status stageof a Control transfer. When an US Processor (11) receives a Setuprequest, it passes the request to the DS Processor (12) as indicated inFIG. 6. The device, instead of responding with an ACK or NAK either inthe data stage, if there is one, or in the Status stage, will respondwith a STALL, which is passed on to the US Processor (11) connected tothe DS Processor (12). Referring to FIG. 6, in such a case the deviceinstead of responding with ACK (129), would reply with a STALL, whichwould be passed on via signals (138) and (139) to the US Processor (11),which would respond with a STALL instead of ACK (114). In this manner,error conditions at both the US and DS connections are handled properlyby the current invention.

In another embodiment of the invention device responses are stored inthe US processor (11). The storage allows for storing STALL responsesthat were received from a device. When the US processor (11) receives aSetup request from the host that would be STALLed by the device, the USprocessor (11) finds the STALL response recorded in its storage andreplies to the host with a STALL.

In another embodiment of the invention device responses are stored inthe Main Controller (10). The storage allows for storing STALL responsesthat were received from a device. When the US processor (11) receives aSetup request from the host it passes that request to the Main Processor(10). When the Main processor (10) examines its storage for a responseto the received request, it finds the STALL response recorded in itsstorage and replies to the host with a STALL via the US processor (11).

FIGS. 8 (a)-(e) demonstrate the use of the data structures of the ATM(63) for the attachment topology of FIG. 8 (e) comprising of two hubsand two devices, for an embodiment of the present invention defined byGroup Definition (301) with a group_size (302) of two and no_groups(303) of one, FIG. 8 (a). There are two DS Processors (12) in thisexample, listed in Group List (304) as ds_1 and ds_2. The topology inFIG. 8 (e) arises when a hub, hub_1 (321) in FIG. 8 (e), is attached toDS Processor (12) ds_1 (320), followed by attachment of device_1 (323)to port 1 of hub_1 (321), then followed by attachment of hub_2 (322) toport 2 of hub_1 (321), then followed by attachment of device _2 (324) toport 4 of hub_2 (322). Device Control (305), FIG. 8 (c) has beeninitialized to group_size (302), making devices_left (317) equal to two.Attachment of device_1 (323) decrements devices_left (317), making itequal to one. Attachment of device _2 (324) also decrements devices_left(317), making it equal to zero, as shown in FIG. 8 (c). Whendevices_left (317) equals zero, any further attachment events at the DSProcessors (12) in the group to which devices_left (317) applies areignored by ATM (63). When hub_1 (321) is attached, the event is reportedto the Main Controller (10) by the DS Processor (12) ds_1 (320). ATM(63) assigns the contents of next_address (306) to the element p_addressin PDL (307), making it equal to one, and increments next_address (306),which will equal two. Information about the attached device obtained byDS Processor (12) ds_1 (320) is used to complete the update of theelement of the PDL (307) corresponding to the peripheral just attached.Since a hub was attached, p_class (311) will equal 9, the class assignedto hubs by the USB specification. In the example of FIG. 8, hub_1 (321)is a full speed hub, and PDL (307) is updated accordingly. Theno_of_ports (315) is set to equal two. Other entries in this element ofthe PDL (307) remain zero. The element higher_hub_address (313) equal tozero indicates that the peripheral described by this element is attacheddirectly. Similarly, port_no (314) remains zero. When device_1 (323) isattached, the event is reported to the Main Controller (10) by the DSProcessor (12) ds_1 (320). ATM (63) assigns the contents of next_address(306) to the element p_address in PDL (307), making it equal to two, andincrements next_address (306), which will equal three. Information aboutthe attached device obtained by DS Processor (12) ds_1 (320) is used tocomplete the update of the element of the PDL (307) corresponding to theperipheral just attached. Since a device, not a hub, was attached,p_class (311) will equal other than 9. In the example of FIG. 8,device_1 (323) is full speed, and PDL (307) is updated accordingly. Theno_of_ports (315) remains zero, since a device was attached. The elementhigher_hub_address (313) equals one, the address of the hub to whichattachment took place. The port_no (314) is made equal to one, the portto which the device was attached. Device Control (305) elementdevices_left (317) is decremented, making it equal to one. When hub_2(322) is attached, the event is reported to the Main Controller (10) bythe DS Processor (12) ds_1 (320). ATM (63) assigns the contents ofnext_address (306) to the element p_address in PDL (307), making itequal to three, and increments next_address (306), which will equalfour. Information about the attached device obtained by DS Processor(12) ds_1 (320) is used to complete the update of the element of the PDL(307) corresponding to the peripheral just attached. Since a hub wasattached, p_class (311) will equal 9, the class assigned to hubs by theUSB specification. In the example of FIG. 8, hub_2 (322) is a full speedhub, and PDL (307) is updated accordingly. The no_of_ports (315) becomesequal to four. Other entries in this element of the PDL (307) remainzero. The element higher_hub_address (313) equals one, the address ofthe hub to which attachment took place. The port_no (314) is made equalto two, the port to which the hub_2 (322) was attached. When device_2(324) is attached, the event is reported to the Main Controller (10) bythe DS Processor (12) ds_1 (320). ATM (63) assigns the contents ofnext_address (306) to the element p_address in PDL (307), making itequal to four, and increments next_address (306), which will equal five.Information about the attached device obtained by DS Processor (12) ds_1(320) is used to complete the update of the element of the PDL (307)corresponding to the peripheral just attached. Since a device, not ahub, was attached, class will equal other than 9. In the example of FIG.8, device_2 (324) is low speed. PDL (307) is updated accordingly. Theno_of_ports (315) remains zero, since a device was attached. The elementhigher_hub_address (313) equals three, the address of the hub to whichattachment took place. The port_no (314) is made equal to four, the portto which the device was attached. Device Control (305) elementdevices_left (317) is decremented, making it equal to zero, therebydisallowing processing of additional attachment events.

The use of the ATM (63) data structures in processing detachment can beunderstood by following detachment of hub_2 (322) in FIG. 8. When hub_2(322) is detached, DS Processor (12) reports to the Main Controller (10)that a detach event occurred at port 2 of hub_1 (321). ATM (63) searchesfor PDL (307) higher_hub_address (313) entries equal to one, the addressof hub_1 and port_no (314) equal to two for a match. It finds that afour-port hub with address three matches. ATM (63) now checks PDL (307)higher_hub_address (313) entries for a match with three, and finds thematch for device with address four. ATM (63) now zeros PDL (307) elemententries for the hub, hub_2 (322), and for the device, device_2 (324). Italso increments the devices_left (317) structure of Device Control(305), making it one, thereby allowing future attachment of anotherdevice to this group, either at DS Processor (12) ds_1 (320) or ds_2. Italso causes the Main Controller (10) to signal the US Processor (11) towhich device_2 (324) was connected to signal detach by generating USBsignal state SE0on the upstream USB signals. The information identifyingthe US Processor (11) to which device_2 (324) was connected is found inthe CM (65).

FIG. 9 shows the structure of the software in accordance with anembodiment of the present invention. A number of US Processes (501)interface with USB hosts (571). A number of DS Processes (503) interfacewith a number of USB-compatible peripherals, hubs or devices (573). TheMain Process (500) controls overall operation, coordinates operation ofthe other processes and bidirectionally routes information and dataamong the US Processes (501) and DS Processes (503). The US Processes(501) are identical, with each US Process (501) being an instantiationserving a different USB host (571). The USB host (571) may represent adirect connection to a host's root hub or a port on an US hub. The DSProcesses (503) are identical, with each DS Process (503) being aninstantiation serving a different DS USB hub or device (573). There maybe more than one device serviced by a DS Process (503), the devicesconnected by a hub or hubs. The USB hosts (571) and USB hubs or devices(573) are not part of the invention and are shown to clarify theapplication of the present invention. The processes shown in FIG. 9operate independently, providing time decoupling between the US and DSsides. It will be understood by one skilled in the art that the numberof US Processes (501) and the number of DS Processes (503) can be moreor less than the number shown in FIG. 9. After power up, all USProcesses (501) issue SE0 signaling to the USB hosts (571) indicatingdetachment. The DS Processes (503) start looking for attachment of USBhub or device (573). When a DS Process (503) detects that a device orhub is attached, it, in cooperation with Main Process (500), determinesthe class of peripheral that is attached, hub or device, and obtainsbasic data about the peripheral. If a hub is attached, it is enumerated,including address assignment, and periodic status requests are startedto determine if a peripheral is attached to one of the hub's ports. Whenit is determined that a peripheral has been attached to one of theports, the examination is repeated. This process continues until thelimit of hubs connected to one another in series as specified in the USBspecification has been reached or until the number of devices reachesthe number allowed for this DS Process (503). Similar to hubs, anexamination of an attached device is performed to obtain basic dataabout the device, including its speed, and an address is assigned to thedevice. Main Controller (500) looks up the identification of the USProcess (501) to which this particular DS Process (503), and thereby theUSB device just attached, should be connected. The connection betweendownstream and upstream is usually specified by a user of the inventionvia User Inputs (506), but can be specified by other means as will bereadily apparent to one skilled in the art. If the connection is active,the SE0 signal state to USB host (571) is removed by a US Process (501)upon command by the Main Process (500) to signal attachment of a device.The Main Process (500) commands an US Process (501) to signal attachmentonly if a device, not a hub, was attached downstream. In this manner,hub attachment downstream is not reflected upstream, permitting the fullconfiguration of five hubs in series on the upstream side. The USB host(571) upon detecting attachment of a device initiates the enumerationprocess. If during the process, or at any other time, USB host (571)issues a Setup request that is not supported by the device attached tothe DS Process (503), said Setup request having been sent from the USProcess (501) to the DS Process (503) via Main Process (500), said Setuprequest will be acknowledged by the device with a STALL handshake. TheSTALL handshake response is passed by the DS Process (503) to the MainProcess (500), which instructs the US Process (501) to reply with aSTALL handshake in the Status stage of the Control transfer thatproduced a STALL response from the device.

FIG. 10 shows the structure of the software of the US Process (501) inaccordance with an embodiment of the present invention. The USCommunications Process—USB (602) manages USB signaling from and to anUSB host (571). Specific signaling situations, such as state SE0generation, loss of activity detection, chirp and squelch signaling forthe high speed case, and resume signaling are also managed by theSignaling Control Process (605). When a packet is being transmitted bythe host, the US Communications Process—USB (602) places the packet inthe Data and Command Storage (610), places the data, if any isassociated with the packet in the Data and Command Storage (610) aswell, and advises the US Control Process (601). US Control Process (601)sends the information in the Data and Command Storage (610) to the MainProcess (500) making use of the services of the US CommunicationsProcess—MP (603). When US Communications Process —MP (603) places datain Data and Command Storage (610) destined for the USB host (571), USControl Process (601) independently manages data toggle synchronizationinsuring correct data transmission to the USB host (571). The USCommunications Process—MP (603) manages communications with the MainProcess (500). One skilled in the art will appreciate that the USCommunications Process—MP (603) is optimized for particularcommunications methods with the Main Process (500), which can includefiber optic communications, Ethernet, TCP/IP, and other methods suitablefor significant distance separation between the US Process (501) and theMain Process (500), and can include local bus interface circuitry. TheHandshake Control Process (604) generates handshake signals required bythe USB Specification within the timing requirements of the USBSpecification. The Handshake Control Process (604) determines the typeof handshake signal to generate if the packets received from the hostare not in error. If the received packets are in error, they are notplaced in the Data and Command Storage (610), and US Control Process(601) is not advised that a packet was received. USB host (571) does notreceive a handshake within the timing requirements of the USBspecification, indicating an error in communications, and handles theerror condition in accordance with its program. Signaling ControlProcess (605) controls the state of the USB signals to USB host (571).When commanded by the Main Process (500), via US Control Process (601),Signaling Control Process (605) removes the SE0 state from the USBsignals and signals the speed commanded by the Main Process (500). Onceattach has been signaled on the USB signals by removing the SE0 state,and USB host (571) issues an USB reset signal, and if the US ControlProcess (601) has reported high speed, the Signaling Control Process(605) initiates the dialog with the USB host defined in the USBSpecification paragraphs 7.1.5 and 7.1.7. If this dialog indicates thata high speed host is present, Signaling Control Process (605) informs USControl Process (600) that a high speed host is present. US ControlProcess (600) in turn informs the Main Process (500) that a high speedhost is present. If Signaling Control Process (605) does not receive thehigh speed response from the USB host (571), it remains a full speeddevice, and informs US Control Process (601) that a high speed host isnot present, which in turn informs the Main Process (500) that a highspeed host is not present. When commanded by Main Process (500), via USControl Process (601), Signaling Control Process (605) also issuesresume signaling to the USB host (571). The US Control Process (601) ineach US Process (501) autonomously coordinates actions of the processescomprising each US Process (501) using information received from theMain Process (500) as needed, thereby providing timing independence fromother US Processes (501) and from DS Processes (503), and allowing theenhancements to USB applications practiced by the present invention.

FIG. 10A shows the structure of the software of the US Process (501) inaccordance with another embodiment of the present invention. Thisembodiment contains all functions of the embodiment shown in FIG. 10 anddescribed above. In addition, it contains a Descriptor Storage (611).Descriptor Storage (611) stores USB descriptors obtained by the DSProcess (503) from a US device associated with this US Processor (501).The descriptors are obtained by the Main Process (501) before deviceattachment is signaled to the host. When device attach is signaled tothe USB host, and the USB host begins the device enumeration sequence,the requests for descriptors are fulfilled from the information in theDescriptor Storage (611).

FIG. 11 shows the structure of the software of the DS Process (503) inaccordance with an embodiment of the present invention. The DSCommunications Process—USB (703) manages USB signaling from and to theUSB hub or device (573). Once a packet has been received from thedevice, the DS Communications Process—USB (703) places the packet in theData and Command Storage (710), places the data, if any is associatedwith the packet in the Data and Command Storage (710) as well andadvises the DS Control Process (701). DS Control Process (701) sends theinformation in the Data and Command Storage (710) to the Main Process(500) making use of the services of the DS Communications Process—MP(702). Data and commands destined to the device sent by the Main Process(500) are placed by the DS Communications Process—MP (702) in the Dataand Command Storage (710). DS Control Process (701) independentlymanages data toggle synchronization insuring correct data transmissionto the USB hub or device (573). The DS Communications Process - USB(703) generates handshake signals to the USB hub or device (573) withinthe time required by the timing requirements of the USB Specification.DS Control Process (701) sends the information in the Data and CommandStorage (710) to the Main Process (500) making use of the services ofthe DS Communications Process—MP (702). The DS Communications Process—MP(702) manages communications with the Main Process (500) and acceptsdata only addressed to the particular DS Process (503). One skilled inthe art will appreciate that the DS Communications Process—MP (702) canbe optimized for particular communications methods with the Main Process(500), which can include such communications methods as fiber opticcommunications, Ethernet, TCP/IP, and other methods suitable forsignificant distance separation between the DS Process (503) and theMain Process (500), and can include local bus interfacing. The DSCommunications Process —USB (703) monitors the state of the DS USBsignals to the USB hub or device (573) and advises the DS ControlProcess (701) when a device is attached and the speed, low or full, ofthe attached peripheral. If the attached peripheral is low speed, TimingGeneration Process (705) starts generating low speed EOP's everymillisecond. If the attached peripheral is full speed, Timing GenerationProcess (705) initiates a dialog with the peripheral to determine if theperipheral is high speed. The dialog is defined in the USB Specificationparagraphs 7.1.5 and 7.1.7. If this dialog indicates that a high speedperipheral is present, Timing Generation Process (705) starts generatinghigh speed SOF's every 125 microseconds. If the dialog indicates that ahigh speed peripheral is not present, Timing Generation Process (705)starts generating full speed SOF's every millisecond. When speed hasbeen determined, DS Communications Process—USB (703) informs DS ControlProcess (701) that a peripheral has been attached and the speed. DSControl Process (701) in turn informs the Main Process (500) that adevice has been attached and reports its speed. Main Process (500)assigns an address to the peripheral and commands the DS Process (503)to obtain additional information about the peripheral. DS ControlProcess (701) sends commands via DS Communications Process—USB (703) toobtain information about the device. If the attached peripheral is ahub, Main Process (500) commands Hub Management Process (706) to startperiodic status inquiries to check if attachments are made to any hubport. If attachment is detected, the Main Process (500) and DS ControlProcess (701) cooperate to determine speed and type of the attachedperipheral. Main Process (500) assigns an address to each newly attachedperipheral until the number of hubs in series exceeds the limit in theUSB specification or the number of devices reaches the number allowedfor this DS Process (503) as specified in the data structures of theMain Process (500). Similarly, when a peripheral, device or hub, isdetached, the event is detected by DS Communications Process—USB (703)or by Hub Management Process (706) if the detach event occurs at a hubport. The event is reported by DS Control Process (701) to the MainProcess (500). Main Process (500) then commands the appropriate USProcess (501) to issue state SE0, signaling detach, to USB host (571).If an USB host (571) issues a command enabling the Remote WakeupFeature, it is noted by the Main Process (500). When subsequently USProcess (501) reports Loss Of Activity, the Main Process (500) commandsthe DS Process (503) to stop generation of the frame timing signals tothe USB hub or device (573). The DS Control Process (701) commandsTiming Generation Process (705) to stop generation of the frame timingsignals to the USB hub or device (573). The DS CommunicationsProcess—USB (703) monitors the state of the signals to the USB hub ordevice (573) and advises the DS Control Process (701) when resumesignaling is detected. DS Control Process (701) passes this informationto the Main Process (500) via DS Communications Process—MP (702). MainProcess (500) then commands the appropriate US Process (501) to issueresume signaling to USB host (571). The DS Control Process (701) in eachDS Process (503) autonomously coordinates actions of the processescomprising each DS Process (503), using information received from theMain Process (500) as needed, thereby providing timing independence fromother DS Processes (503) and from US Processes (501), and allowing theenhancements to USB applications practiced by the present invention.

FIG. 12 shows the structure of the software of the Main Process (500) inaccordance with an embodiment of the present invention. Main Process(500) coordinates US Processes (501) and DS Processes (503), alloperating independently; routes information bidirectionally among DSProcesses (503) and US Processes (501); maintains information about theattachment topology of hubs and devices attached to the DS Processes;and provides facilities for user control and indications. ExecutionControl Process (ECP) (801) controls and coordinates the functionalcomponents of the Main Process (500). Display Control Process (806)provides system state indications from information existing within theMain Process (500), such as in the Connection Control Process (804).Among the functions available via the User Interface Process (805) isswitching of devices to hosts by providing information to the ConnectionControl Process (804). Routing Control Process (808) provides physicaladdressing information and directs information flow from/to US Processes(501) and DS Processes (503). In addition to using information from theConnection Control Process (804), Routing Control Process (808) usesinformation in messages stored in the Data and Command Storage (DCS)(810) to determine the destination. Routing Control Process (808) alsoremaps device addresses assigned by an USB host (571), as reported by anUS Process (501), to device addresses assigned to a device by AttachmentTopology Process (807).

Communications Process—US (802) manages communications with US Processes(501). Communications Process—DS (803) manages communications with DSProcesses (503). A practitioner of ordinary skill in the art willunderstand that the communications method with the US Processes (501)and the communications method with the DS Processes (503) may bedifferent from each other in nature, or that they may be of the samenature. The communications method can be the most suitable for theintended application, and can include fiber optic communications,Ethernet, TCP/IP, and other methods suitable for significant distanceseparation between the US Processes (501), the Main Process (500), andcan include local bus interfacing. Attachment Topology Process (ATP)(807) receives and processes reports of peripheral attachment anddetachment reported by the DS Processes (503). The current downstreamattachment topology and address assignment are held in data structuresunique for each DS Process (503) and in global data structures. The ATP(807) data structures are illustrated in FIG. 7. FIG. 7 (a) and (b) showglobal data structures Group Definition (301) and Group List (304),respectively. Group Definition (301) specifies the number of DSProcesses (503) in a group in group_size (302) and the number of groupsin no_groups (303). The Group List (304) specifies which DS Processes(503) are part of one group, and contains a number of lists equal to thenumber of groups, specified in no_groups (303). FIG. 7 (c) shows theDevice Control (305) data structure, which contains an element,devices_left_j (317), for each group. Device Control (305) controls thenumber of devices that can be attached to DS Processes (503) in onegroup. Each element, devices_left_j (317), is dynamically controlled asdevices are attached and detached. FIG. 7 (d) shows the data structurenext_address (306) and Peripheral_Definition_List (PDL) (307), whichexists for each DS Process (503). The PDL (307) entries p_address (310),p_class (311), p_speed (312), higher_hub_address (313), port_no (314),and no_of_ports (315) form one element of the PDL (307). The number ofelements dynamically increases and decreases during operation as devicesand hubs are attached and detached.

FIG. 12A shows another embodiment of the Main Process (500) that allowsunlimited separation distance between an USB host and an USB devicewhile supplying true enumeration data to the host. The Main Process(500) in this embodiment contains all functions of the embodiment shownin FIG. 12 and described above. In addition, it contains a DescriptorStorage (811). The Descriptor Storage (811) stores USB descriptorsobtained by the DS Process (503) from a USB device upon commend from theMain Process (500). Execution Control Process (801) in this embodimentcommands the DS Process (503) to perform a complete enumeration of theUSB device, obtaining all standard and class descriptors as specified inthe USB Specification. The descriptors are supplied to the USB host fromDescriptor Storage (811) via the US Process (501) in response todescriptor requests issued by the USB host.

It is appreciated that the term storage as used herein is any knownstorage device, such as disk storage, file storage system, internal orexternal memory, flash drive and the like. Also, it is appreciated thatthe computer readable medium is a tangible storage device for storingcomputer executable instructions, such as memory, CD, DVD, flash driveand the like.

The methods and systems described above overcome the limitations of theUSB specification given above and of the prior art and permitenhancements in connection separation length between USB-compliantdevices and USB hosts, in switching one or more USB-compliant devicesamong many USB hosts and in connecting many USB-compliant devices to thesame USB host with control over their communications such that they donot interfere with one another. No changes or modifications are neededto USB hosts, hubs or USB-compliant devices; standard hosts, hubs anddevices can be used with the current invention. It will be understoodthat alternatives, modifications and variations thereof may be suggestedto those skilled in the art.

1-24. (canceled)
 25. An automatic mapping and updating computerswitching device for automatic executing enumeration between a pluralityof peripheral devices and a plurality of computers, comprising: a USBhost chip electrically connected to said peripheral devices; and aplurality of USB device chips electrically connected between said USBhost chip and said computers; wherein, in a standard USB procedure forstandard USB devices which are connected as peripheral devices, which isperformed when said computer switching device is turned on, said USBhost chip acts as a computer to receive the enumeration command/datafrom the peripheral device and stores the enumeration command/data in aUSB host chip memory, and said USB host chip transfers the enumerationcommand/data to said USB device chip and said USB device chip stores thetransferred enumeration command/data in a USB device chip memory, andsaid USB device chip acts as a peripheral device to transfer theenumeration command/data to the computer, so that the peripheral deviceis enumerated by the USB host chip as a standard USB device, wherein allthe enumeration command/data in the above procedure are recorded in saidUSB host chip and said USB device chip, wherein, in a comparisonprocedure, where the enumeration command/data of the previouslyconnected peripheral device is stored, as an old enumerationcommand/data, in the USB host chip memory, and the enumerationcommand/data of a plugged/unplugged peripheral device is as a newenumeration command/data, and the comparison procedure which isperformed when said automatic mapping and updating computer switchingdevice re-boots or any of said peripheral devices is plugged/unplugged,the USB host chip performs the comparison of the old stored enumerationcommand/data with the new enumeration command/data, and if the result ofthe comparison is the same, the USB host chip performs nothing, or ifthere is any difference therebetween, the USB host chip performs thestandard USB procedure for each peripheral device, wherein all of therespective enumeration command/data for each of the peripheral devicesenumerated as a standard USB device in the previous procedures aretransferred by the USB host device chip to all of the USB device chips.